Skip to content

Hostname

transangels.com

Last fetched

transangels.com resolves to 66.254.114.234, announced in 66.254.114.0/24 by REFLECTED - Reflected Networks, Inc. in ES. transangels.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 · transangels.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/transangels.com

Resolution chain

IPv6 resolution

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

Attribution

reflected

ORIGIN_AS

WHOIS identity

Registrar
iana:1052
Registrant organisation
domain admin / this domain is for sale
Contact emails
98d72723bfd5f607_o@whoisprivacy.com, domains@hugedomains.com

Subdomains

Subdomain
land.transangels.com
ma.transangels.com
probiller.transangels.com
site-ma.transangels.com
site-tour.transangels.com
support.transangels.com
www.transangels.com

Showing 7 of 7 subdomains (7 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

Sample outbound links

Mail and authentication

Nameservers

  • sdns3.ultradns.biz
  • ns-92.awsdns-11.com
  • sdns3.ultradns.com
  • ns-531.awsdns-02.net
  • sdns3.ultradns.net
  • ns-1499.awsdns-59.org
  • sdns3.ultradns.org
  • ns-1567.awsdns-03.co.uk

MX records

  • mxa-002a0701.gslb.pphosted.com
  • mxb-002a0701.gslb.pphosted.com

SPF policy

  • include: spf.protection.outlook.com
  • include: spf-002a0701.pphosted.com
  • mx: transangels.com
  • ip: 162.211.96.66
  • ip: 162.211.96.67

Threat-feed evidence

History

Related pages

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