diff --git a/content/docs/deliverability/spf-and-ip4-mechanisms.md b/content/docs/deliverability/spf-and-ip4-mechanisms.md
index 087221aa..fdd21b51 100644
--- a/content/docs/deliverability/spf-and-ip4-mechanisms.md
+++ b/content/docs/deliverability/spf-and-ip4-mechanisms.md
@@ -13,5 +13,3 @@ We recognize that SPF 7208 says the ptr mechanism **SHOULD NOT** be used, but it
 **Note**: This mechanism is slow, it is not as reliable as other mechanisms in cases of DNS errors, and it places a large burden on the .arpa name servers.  If used, proper PTR records have to be in place for the domain's hosts and the "ptr" mechanism **SHOULD** be one of the last mechanisms checked.  After many years of SPF deployment experience, it has been concluded that it is unnecessary and more reliable alternatives should be used instead.  It is, however, still in use as part of the SPF protocol, so compliant check_host() implementations **MUST** support it.
 
 We recognize that our SPF record does not pass muster with sites such as [dmarcian.com](http://dmarcian.com/), but rest assured that it does result in verdicts of pass on mail sent using the SPF record we publish.
-
-You can also use our SPF tools for your SPF needs [SPF Inspector](https://tools.sparkpost.com/spf/inspector) and [SPF Builder](https://tools.sparkpost.com/spf/builder).