Domain
api.aws
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of api.aws
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
Hosting IPs
46,598
A/AAAA targets
Subdomains
24,815
CT + scan + body
Record Types
1
seen in DNS
Observed Certs
—
in our scans
DNS Records
A
—
AAAA
—
MX
—
NS
—
TXT
—
CNAME
—
CAA
—
WHOIS / Registration
Registration data planned
Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.
Subdomains
Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
Subject: *.ec2-instance-connect-endpoint.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.2ef6b67f.ec2-instance-connect-endpoint.us-gov-west-1.api.aws, *.ec2-instance-connect-endpoint.us-gov-west-1.api.aws
Subject: application-signals-gamma.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.application-signals-gamma.us-gov-west-1.vpce.amazonaws.com, application-signals-gamma.us-gov-west-1.api.aws
Subject: s3vectors.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: *.s3vectors.us-gov-west-1.vpce.amazonaws.com, s3vectors.us-gov-west-1.api.aws
Subject: lb-c01-osu62.eks-auth.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: *.eks-auth.us-gov-east-1.vpce.amazonaws.com, eks-auth-fips.us-gov-east-1.api.aws, eks-auth.us-gov-east-1.api.aws, lb-c01-osu62.eks-auth.us-gov-east-1.api.aws, osu62.eks-auth.us-gov-east-1.api.aws
Subject: topology.application-signals-staging-fips.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: topology.application-signals-staging-fips.us-gov-east-1.api.aws
Subject: lambda.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.api-lambda.us-gov-west-1.api.aws, lambda.us-gov-west-1.api.aws
Subject: lambda.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: *.api-lambda.us-gov-east-1.api.aws, lambda.us-gov-east-1.api.aws
Subject: gamma-notifications.ap-southeast-3.api.aws
Issuer: Amazon RSA 2048 M04
SANs: *.gamma-notifications.ap-southeast-3.vpce.amazonaws.com, gamma-notifications.ap-southeast-3.amazonaws.com, gamma-notifications.ap-southeast-3.api.aws
Subject: s3-hrs-syd.ap-southeast-2.api.aws
Issuer: Amazon RSA 2048 M04
SANs: s3-hrs-syd.ap-southeast-2.api.aws
Subject: lambda.us-east-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.api-lambda.us-east-1.api.aws, lambda.us-east-1.api.aws
Subject: application-signals-staging.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.application-signals-staging.us-gov-west-1.vpce.amazonaws.com, application-signals-staging.us-gov-west-1.api.aws
Subject: s3-hrs-osu.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: s3-hrs-osu.us-gov-east-1.api.aws
Subject: ecncontroller-rms-1.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: ecncontroller-rms-1.us-gov-east-1.api.aws
Subject: emr-service-cell01.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: *.emr-service-cell01.us-gov-east-1.vpce.amazonaws.com, emr-service-cell01.us-gov-east-1.api.aws
Subject: workspaces-instances-gamma.me-central-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: workspaces-instances-gamma.me-central-1.api.aws
Subject: us-gov-west-1.gamma.fips.frontend.cloudapi.aws.dev
Issuer: Amazon RSA 2048 M04
SANs: us-gov-west-1.gamma.fips.frontend.cloudapi.aws.dev
Subject: centaur-gamma.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: centaur-gamma.us-gov-west-1.api.aws
Subject: *.cell-0-sync-invoke-service-lambda.me-central-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.cell-0-sync-invoke-service-lambda.me-central-1.api.aws
Subject: topology.application-signals.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: topology.application-signals.us-gov-west-1.api.aws
Subject: *.fips.ec2-instance-connect-endpoint.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: *.c8334461.fips.ec2-instance-connect-endpoint.us-gov-east-1.api.aws, *.fips.ec2-instance-connect-endpoint.us-gov-east-1.api.aws
Subject: centaur-gamma-fips.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: centaur-gamma-fips.us-gov-west-1.api.aws
Subject: *.fips.ec2-instance-connect-endpoint.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: *.c8334461.fips.ec2-instance-connect-endpoint.us-gov-east-1.api.aws, *.fips.ec2-instance-connect-endpoint.us-gov-east-1.api.aws
Subject: miapi.awsapp.cn
Issuer: Amazon RSA 2048 M01
SANs: miapi.awsapp.cn
Subject: redshift-data-integ.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.integ.redshift-data.us-gov-east-1.vpce.amazonaws.com, *.redshift-data-integ.us-gov-east-1.api.aws, redshift-data-integ.us-gov-east-1.api.aws
Subject: athena.us-gov-east-1.api.aws
Issuer: Amazon RSA 2048 M04
SANs: athena.us-gov-east-1.api.aws
Subject: application-signals-gamma.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.application-signals-gamma.us-gov-west-1.vpce.amazonaws.com, application-signals-gamma.us-gov-west-1.api.aws
Subject: application-signals-gamma.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.application-signals-gamma.us-gov-west-1.vpce.amazonaws.com, application-signals-gamma.us-gov-west-1.api.aws
Subject: *.ec2-instance-connect-endpoint.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: *.2ef6b67f.ec2-instance-connect-endpoint.us-gov-west-1.api.aws, *.ec2-instance-connect-endpoint.us-gov-west-1.api.aws
Subject: redshift-data-integ.me-central-1.api.aws
Issuer: Amazon RSA 2048 M02
SANs: *.integ.redshift-data.me-central-1.vpce.amazonaws.com, *.redshift-data-integ.me-central-1.api.aws, redshift-data-integ.me-central-1.api.aws
Subject: runtime-v2-lex-gamma.us-gov-west-1.api.aws
Issuer: Amazon RSA 2048 M01
SANs: runtime-v2-lex-gamma.us-gov-west-1.api.aws
IPs Citing This Domain
No citing IPs found yet
As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.
Origin / IP-Leak
USP
When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.
No origin-IP leaks detected (yet)
Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.
Threat Intelligence
Domain threat-intel pending
Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.
History
Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.
| Type | Value | First seen | Last seen |
|---|---|---|---|
| NS | ns-1471.awsdns-55.org | 2026-06-01 19:43:46.544 | 2026-07-15 20:04:13.980 |
| NS | ns-662.awsdns-18.net | 2026-06-01 19:43:46.544 | 2026-07-15 20:04:13.980 |
| NS | ns-225.awsdns-28.com | 2026-06-01 19:43:46.544 | 2026-07-15 20:04:13.980 |
| NS | ns-1805.awsdns-33.co.uk | 2026-06-01 19:43:46.544 | 2026-07-15 20:04:13.980 |