Skip to content

Hostname

trinity-bg.org

Last fetched

trinity-bg.org resolves to 185.80.2.209, announced in 185.80.2.0/23 by SUPERHOSTING_AS - SuperHosting.BG Ltd. in BG. trinity-bg.org 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 · trinity-bg.orgRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/trinity-bg.org

Resolution chain

IPv6 resolution

No AAAA record for trinity-bg.org is recorded in WhisperGraph.

Attribution

superhosting bg

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:48
Registrant organisation
danail radkov
Contact emails
radkovy@abv.bg

Subdomains

Subdomain
autodiscover.trinity-bg.org
cpanel.trinity-bg.org
cpcalendars.trinity-bg.org
cpcontacts.trinity-bg.org
mail.trinity-bg.org
webdisk.trinity-bg.org
webmail.trinity-bg.org
www.trinity-bg.org

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

  • ns281.superhosting.bg
  • ns282.superhosting.bg

MX records

  • trinity-bg.org

SPF policy

  • ip: 185.45.67.18/32
  • include: lima.spf.superhosting.bg
  • include: mini.spf.superhosting.bg
  • include: smtp-out.spf.superhosting.bg
  • a: trinity-bg.org
  • mx: trinity-bg.org
  • ip: 164.138.218.19
  • ip: 164.138.219.19
  • ip: 185.45.66.18
  • ip: 185.80.2.85
  • ip: 185.80.3.85

Threat-feed evidence

History

Related pages

Pivot from trinity-bg.org 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: "trinity-bg.org"})-[: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.