Hostname
pbpstats.com
Last fetched
pbpstats.com resolves to 16.15.176.41, announced in 16.15.176.0/21 by AMAZON-AES - Amazon.com, Inc. in US. pbpstats.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 16.15.176.41
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.180.138
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.187.125
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.187.32
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.188.55
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.191.162
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.191.207
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.193.1
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.199.15
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.199.249
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.207.122
16.15.200.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.216.143
16.15.216.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.182.35.229
16.182.32.0/21 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.216.10.122
52.216.10.0/24 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.216.216.253
52.216.208.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.216.33.69
52.216.32.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.216.49.189
52.216.48.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.217.123.181
52.217.112.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.217.125.189
52.217.112.0/20 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
- 52.217.138.117
52.217.128.0/19 · AMAZON-02 - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for pbpstats.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of pbpstats.com owner
- Contact emails
- 54839123-b733-488f-b173-a1d1af5ed7a9@identity-protect.org, 82e581f8-b030-4b59-be60-4c9c753cdb14@identity-protect.org, fa43540f-0fbc-45c1-84e1-c213d7e60725@identity-protect.org, owner-1105298@pbpstats.com.whoisprivacyservice.org, owner-5439891@pbpstats.com.whoisprivacyservice.org
Company
- Company
- PBP Stats
Technology
PBP Stats has been observed using 7 technologies somewhere in its estate. This is observed use, not an exposure finding.
- Amazon Web Services · cloud hosting
- Vue.js · javascript frameworks
- Amazon S3 · content delivery network
- Amazon Route 53 · domain name services
- Amazon CloudFront · content delivery network
- Patreon · payment processing
- GoatCounter · analytics
Subdomains
Showing 3 of 3 subdomains (3 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
DNSSEC
WhisperGraph records no DNSSEC signature for pbpstats.com.
DKIM signing
No DKIM signing vendor is attributed to pbpstats.com in WhisperGraph.
Nameservers
- ns-347.awsdns-43.com
- ns-856.awsdns-43.net
- ns-1051.awsdns-03.org
- ns-1667.awsdns-16.co.uk
Threat-feed evidence
History
Related pages
Pivot from pbpstats.com into the addresses, networks and registries it depends on.
Queries
This hostname's full card — resolution chain, registration, mail policy, DNSSEC and mail authentication.
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(ip:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap)
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (ip)-[:LOCATED_IN]->(city:CITY)
OPTIONAL MATCH (ip)-[:HAS_COUNTRY]->(ipc:COUNTRY)
WITH h, ip, ap, a, an, city, ipc
LIMIT 20
WITH h,
collect({ip: ip.name, prefix: ap.name, asn: a.name, network: an.name, city: city.name, country: ipc.name}) AS resolutions,
collect(a.name) AS asnNames,
collect(ap.name) AS prefixNames,
collect(ap.isMoas) AS moasFlags,
collect(ap.rpkiStatus) AS rpkiStatuses,
head(collect(a)) AS primaryAsn,
head(collect(ap)) AS primaryPrefix
OPTIONAL MATCH (primaryPrefix)-[:CONFLICTS_WITH]->(conflict:ASN)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn,
collect(conflict.name) AS conflictAsns
OPTIONAL MATCH (h)-[:HAS_REGISTRAR]->(reg:REGISTRAR)
OPTIONAL MATCH (h)-[:REGISTERED_BY]->(org:ORGANIZATION)
OPTIONAL MATCH (h)-[:CHILD_OF]->(tld:TLD)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
collect(reg.name) AS registrars,
collect(org.name) AS organizations,
collect(tld.name) AS tlds
OPTIONAL MATCH (h)-[:HAS_EMAIL]->(em:EMAIL)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds,
collect(em.name) AS emails
OPTIONAL MATCH (h)-[:HAS_PHONE]->(ph:PHONE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails,
count(ph) AS phoneCount
OPTIONAL MATCH (h)<-[:MAIL_FOR]-(mx:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount,
collect(mx.name)[0..20] AS mxHosts
OPTIONAL MATCH (h)<-[:NAMESERVER_FOR]-(ns:HOSTNAME)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts,
collect(ns.name) AS nameservers
OPTIONAL MATCH (h)-[spf:SPF_A|SPF_EXISTS|SPF_INCLUDE|SPF_IP|SPF_MX|SPF_REDIRECT]->(spfTarget)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers,
collect({mechanism: type(spf), target: spfTarget.name})[0..50] AS spf
OPTIONAL MATCH (h)-[:SIGNED_WITH]->(alg:DNSSEC_ALGORITHM)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
collect(alg.name) AS dnssecAlgorithms
OPTIONAL MATCH (h)-[:DMARC_REPORTS_TO]->(dm:DMARC_RECIPIENT)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
collect(dm.name)[0..5] AS dmarcRecipients
OPTIONAL MATCH (h)-[:DKIM_SIGNED_BY]->(dk:VENDOR)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients,
collect(coalesce(dk.displayName, dk.name))[0..5] AS dkimVendors
OPTIONAL MATCH (h)-[:HAS_SIGNAL]->(hs:THREAT_SIGNAL_TYPE)
WITH h, resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, primaryAsn, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf, dnssecAlgorithms,
dmarcRecipients, dkimVendors,
collect(hs.name) AS dnsSignals
CALL { WITH primaryAsn MATCH (primaryAsn)-[:BGP_NEIGHBOR]-(peer:ASN) RETURN count(peer) AS asnPeerCount }
RETURN h.name AS name,
h.rank AS rank,
h.verdictLevel AS verdictLevel,
h.verdictScore AS verdictScore,
h.verdictBlocking AS verdictBlocking,
h.verdictCoverage AS verdictCoverage,
h.verdictAdvisory AS verdictAdvisory,
h.threatSources AS threatSources,
h.threatFirstSeen AS threatFirstSeen,
h.threatLastSeen AS threatLastSeen,
h.isTor AS isTor,
h.isVpn AS isVpn,
h.isProxy AS isProxy,
h.isC2 AS isC2,
h.isPhishing AS isPhishing,
resolutions, asnNames, prefixNames, moasFlags, rpkiStatuses, conflictAsns,
registrars, organizations, tlds, emails, phoneCount, mxHosts, nameservers, spf,
dnssecAlgorithms, dmarcRecipients, dkimVendors, dnsSignals,
h.companyName AS companyName,
h.companyIndustry AS companyIndustry,
h.companyHqCountry AS companyHqCountry,
h.companyHqCity AS companyHqCity,
asnPeerCountRun yourself →The observed subdomain count, to depth 3.
MATCH (h:HOSTNAME {name: $host})
CALL { WITH h MATCH (h)<-[:CHILD_OF*1..3]-(sub:HOSTNAME) RETURN count(sub) AS subdomainCount }
RETURN subdomainCountRun yourself →Technologies the company behind this domain has been observed running, most widely adopted first.
MATCH (:HOSTNAME {name: $host})-[:RUNS_TECHNOLOGY]->(t:TECHNOLOGY)
WITH t.name AS name, t.category AS category, t.adopterCount AS adopters
ORDER BY adopters DESC, name
WITH collect({name: name, category: category}) AS technologies, count(*) AS total
RETURN total, technologies[0..20] AS technologiesRun yourself →Peer companies (outbound SIMILAR_TO).
MATCH (:HOSTNAME {name: $host})-[:SIMILAR_TO]->(peer:HOSTNAME) RETURN peer.name AS host ORDER BY host LIMIT 8Run yourself →The parent company's domain and this company's domain portfolio (PARENT_OF).
MATCH (h:HOSTNAME {name: $host})
OPTIONAL MATCH (h)<-[:PARENT_OF]-(parent:HOSTNAME)
WITH h, collect({host: parent.name, company: parent.companyName})[0..3] AS parents
OPTIONAL MATCH (h)-[:PARENT_OF]->(child:HOSTNAME)
RETURN parents, collect({host: child.name, company: child.companyName})[0..10] AS portfolioRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.