Skip to content

Hostname

timss2019.org

Last fetched

timss2019.org resolves to 3.224.66.250, announced in 3.224.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. timss2019.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 · timss2019.orgRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/timss2019.org

Resolution chain

IPv6 resolution

No AAAA record for timss2019.org is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:955
Registrant organisation
boston college
Contact emails
yenpa84@gmail.com, timssandpirls@bc.edu

Subdomains

Subdomain
autodiscover.timss2019.org
cpanel.timss2019.org
cpcalendars.timss2019.org
cpcontacts.timss2019.org
mail.timss2019.org
webdisk.timss2019.org
webmail.timss2019.org
www.timss2019.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

  • cns31.hostgator.com
  • cns32.hostgator.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mail.timss2019.org

SPF policy

  • include: websitewelcome.com
  • a: timss2019.org
  • mx: timss2019.org

Threat-feed evidence

History

Related pages

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