Skip to content

Hostname

regain.com

Last fetched

regain.com resolves to 166.117.115.19, announced in 166.117.112.0/20 by AMAZON-02 - Amazon.com, Inc. in US. regain.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · regain.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/regain.com

Resolution chain

IPv6 resolution

No AAAA record for regain.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
charlie mason
Contact emails
regain.com@domainsbyproxy.com, info@heavylifting.com, 4d89b1ac-9e88-46a0-a059-35be1022a7c1@identity-protect.org, 549cc2e3-169b-4d5c-a3e7-08ec78bcebd3@identity-protect.org, a6da0a01-dff4-4198-9dac-c0c142fe1bab@identity-protect.org, c3f86d7e-738a-4251-bc2f-df0a02f09f42@identity-protect.org

Subdomains

Subdomain
links.regain.com
staging.regain.com
www.regain.com

Showing 3 of 10. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • ns-470.awsdns-58.com
  • ns-842.awsdns-41.net
  • ns-1339.awsdns-39.org
  • ns-1588.awsdns-06.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: helpscoutemail.com
  • include: spf_c.oraclecloud.com
  • include: _spf.salesforce.com
  • include: servers.mcsv.net

Threat-feed evidence

History

Related pages

Pivot from regain.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: "regain.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.