Hostname
pokemonpets.com
Last fetched
pokemonpets.com resolves to 38.154.104.227, announced in 38.154.96.0/19 by SERVER-MANIA - B2 Net Solutions Inc. in US. pokemonpets.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
- 38.154.104.227
38.154.96.0/19 · SERVER-MANIA - B2 Net Solutions Inc. · Buffalo, US
IPv6 resolution
No AAAA record for pokemonpets.com is recorded in WhisperGraph.
Attribution
b2 net
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- furkan g?z?kara
- Contact emails
- cefurkan@hotmail.com, 58d9c9bc106d4198a8f7b8aa02bd32c6.protect@whoisguard.com, 5e6133226cd1418693a9db12671f3cd6.protect@whoisguard.com, 7b81f51ce2b047babc66d2ff93ca4e62.protect@whoisguard.com, daa631776515438fb39c5e91667b41da.protect@whoisguard.com, 0c43735abec04b23a1711e765c1d98e4.protect@withheldforprivacy.com, 8ade34e5626443688c22b8550faaf68c.protect@withheldforprivacy.com
Subdomains
Showing 4 of 4 subdomains (4 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.
Sample inbound links
Mail and authentication
Nameservers
- ns-cloud-e1.googledomains.com
- ns-cloud-e2.googledomains.com
- ns-cloud-e3.googledomains.com
- ns-cloud-e4.googledomains.com
- dns1.registrar-servers.com
- dns2.registrar-servers.com
MX records
- eforward1.registrar-servers.com
- eforward2.registrar-servers.com
- eforward3.registrar-servers.com
- eforward4.registrar-servers.com
- eforward5.registrar-servers.com
SPF policy
- ip: 198.154.81.17/29
- ip: 38.154.104.224/27
- ip: 198.245.73.80/29
- include: monstermmorpg.com
- include: pokemonpets.com
- include: spf.efwd.registrar-servers.com
Threat-feed evidence
History
Related pages
Pivot from pokemonpets.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "pokemonpets.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.