Hostname
peigenesis.com
Last fetched
peigenesis.com resolves to 4 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:2 as the registrar.
Nutrition Label
Resolution chain
peigenesis.com resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.20.39.216 | 104.20.32.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.66.153.137 | 172.66.144.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 80.93.202.253 | 80.93.202.0/24 | AS209242 | MCPL-AS | US |
| 80.93.202.254 | 80.93.202.0/24 | AS209242 | MCPL-AS | US |
WHOIS identity
- Registrar
- iana:2
- Organization
- pei-genesis,
- Contact emails
Subdomains
64 observed subdomains of peigenesis.com.
Showing 25 of 64. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from peigenesis.com in the public web crawl.
226 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
13 SPF mechanisms authorising senders for peigenesis.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | 2688824.spf02.hubspotemail.net |
| SPF_INCLUDE | _netblocks.mimecast.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 148.59.100.16/28 |
| SPF_IP | 148.59.101.16/28 |
| SPF_IP | 167.89.112.57/24 |
| SPF_IP | 168.245.61.196 |
| SPF_IP | 18.168.140.58/32 |
| SPF_IP | 18.168.51.200/32 |
| SPF_IP | 35.80.141.6/32 |
| SPF_IP | 44.229.121.55/32 |
| SPF_IP | 8.39.113.127 |
| SPF_IP | 8.39.98.127 |
Related pages
Pivot deeper into the graph from peigenesis.com.
- IP · 104.20.39.216
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:2
- Country · CA
- Email · no.valid.email@worldnic.com
- TLD · .com
- Browse hostnames · pe…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "peigenesis.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.