Skip to content

Hostname

shiftboard.com

Last fetched

shiftboard.com resolves to 100.20.224.18, announced in 100.20.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. shiftboard.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 · shiftboard.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/shiftboard.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:299
Registrant organisation
******** ******** (see notes section below on how to view unmasked data)
Contact emails
********@*****.***, dns@shiftboard.net

Subdomains

Subdomain
app.shiftboard.com
blog.shiftboard.com
eu.shiftboard.com
express.shiftboard.com
info.shiftboard.com
login.shiftboard.com
m.shiftboard.com
messaging.shiftboard.com
support.shiftboard.com
timeclock.shiftboard.com
www.shiftboard.com
zabbix.shiftboard.com

Showing 12 of 13. 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-269.awsdns-33.com
  • ns-723.awsdns-26.net
  • ns-1039.awsdns-01.org
  • ns-1954.awsdns-52.co.uk

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • include: us._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: stspg-customer.com
  • include: mail.zendesk.com
  • include: 2059219.spf02.hubspotemail.net
  • include: _spf.mailgun.org
  • include: _spf.eu.mailgun.org

Threat-feed evidence

History

Related pages

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