Hostname
regence.com
Last fetched
regence.com resolves to 1 IPv4 address operated by INCAPSULA - Incapsula Inc in US. WHOIS lists iana:2 as the registrar.
Nutrition Label
Resolution chain
regence.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 45.60.233.13 | 45.60.233.0/24 | AS19551 | INCAPSULA - Incapsula Inc | US |
WHOIS identity
- Registrar
- iana:2
- Organization
- cambia health solutions
- Contact emails
- aa36s6p852t@networksolutionsprivateregistration.com
- christine.antonson@cambiahealth.com
- c55j74xe4ha@networksolutionsprivateregistration.com
- df5vh4876ec@networksolutionsprivateregistration.com
- dns_admins@regence.com
- gy7vy8qj2rb@networksolutionsprivateregistration.com
- hx8uk2tk7bb@networksolutionsprivateregistration.com
- walter.mezs@cambiahealth.com
- ry9zn3mh66v@networksolutionsprivateregistration.com
- tv8d93wc8jt@networksolutionsprivateregistration.com
- wu9hg59m8uk@networksolutionsprivateregistration.com
- zw2qc74f2xf@networksolutionsprivateregistration.com
Subdomains
146 observed subdomains of regence.com.
Showing 25 of 146. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from regence.com in the public web crawl.
744 sites link to this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
2 SPF mechanisms authorising senders for regence.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf1.regence.com |
| SPF_INCLUDE | spf2.regence.com |
Related pages
Pivot deeper into the graph from regence.com.
- IP · 45.60.233.13
- ASN · AS19551INCAPSULA - Incapsula Inc
- Registrar · iana:2
- Country · US
- Email · aa36s6p852t@networksolutionsprivateregistration.com
- TLD · .com
- Browse hostnames · re…
- 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: "regence.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.